Management device, management method, and computer program product

ABSTRACT

A management device that manages a task that is executed by a plurality of users cooperatively includes an electronic data access unit, a management unit, and a past task storage unit. The electronic data access unit accesses electronic data. The management unit manages, for each task executed using the management device, task information in which pieces of authentication information of the users who have participated in the task are associated with access destination information indicating an access destination of the electronic data accessed by the electronic data access unit in the task. The past task storage unit stores therein the task information of a past task executed using the management device. The management unit generates the task information of a new task based on the task information of the past task that is stored in the past task storage unit.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims priority to and incorporates by referencethe entire contents of Japanese Patent Application No. 2015-056984 filedin Japan on Mar. 19, 2015.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a management device, a managementmethod, and a computer program product.

2. Description of the Related Art

A plurality of users carry out a task using one device cooperatively insome cases. For example, a plurality of users carry out a task using oneinteractive whiteboard (electronic blackboard) cooperatively in somecases. In this case, a situation where the users carry out the task byreferring to electronic data through the interactive whiteboard canoccur. It is conceivable that the users access electronic data, forexample, a first document created by a first user previously and asecond document created by a second user previously.

Furthermore, for example, another task different in combination ofparticipant users is carried out in a different period of time or a taskwith the same combination of users is carried out regularly using thesame interactive whiteboard in some cases. The participating user leavesthe task in the middle, a task theme is changed or divided, or aplurality of task themes are integrated in some cases.

In these cases, for example, a manager needs to execute, for the device(for example, interactive whiteboard) that is used cooperatively,procedures such as creation of a new task, registration of users of eachtask, and deletion of an unnecessary task. Accordingly, a burden on themanager increases undesirably. Furthermore, increase in the number ofusers who can be the managers causes a security problem more seriously.

Therefore, there is a need for a management device, a management method,and a computer program product that enable a new task to be easily setwhen a plurality of users carry out the task cooperatively.

SUMMARY OF THE INVENTION

It is an object of the present invention to at least partially solve theproblems in the conventional technology.

According to an embodiment, a management device that manages a task thatis executed by a plurality of users cooperatively includes an electronicdata access unit, a management unit, and a past task storage unit. Theelectronic data access unit accesses electronic data. The managementunit manages, for each task executed using the management device, taskinformation in which pieces of authentication information of the userswho have participated in the task are associated with access destinationinformation indicating an access destination of the electronic dataaccessed by the electronic data access unit in the task. The past taskstorage unit stores therein the task information of a past task executedusing the management device. The management unit generates the taskinformation of a new task based on the task information of the past taskthat is stored in the past task storage unit.

The above and other objects, features, advantages and technical andindustrial significance of this invention will be better understood byreading the following detailed description of presently preferredembodiments of the invention, when considered in connection with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating the configuration of a managementsystem according to an embodiment;

FIG. 2 is a diagram illustrating the functional configuration of amanagement device;

FIG. 3 is a diagram illustrating an example of task information of atask that is being executed;

FIG. 4 is a diagram illustrating an example of pieces of taskinformation of past tasks;

FIG. 5 is a flowchart illustrating processing when a task is started;

FIG. 6 is a flowchart illustrating processing when a document isaccessed;

FIG. 7 is a flowchart illustrating processing when a task is finished;

FIG. 8 is a sequence diagram illustrating processing when a terminaldevice accesses a document after a task is finished;

FIG. 9 is a diagram illustrating examples of login timings and logouttimings of users and the users that have participated in each task;

FIG. 10 is a diagram illustrating examples of the login timings and thelogout timings of the users and documents that are used in each task;

FIG. 11 is a diagram illustrating task information of a new task takingover a past task;

FIG. 12 is a flowchart illustrating processing when the new task isstarted while taking over the past task;

FIG. 13 is a diagram illustrating task information of a new task createdby combining a plurality of past tasks;

FIG. 14 is a flowchart illustrating processing when the past tasks arecombined and the new task is started;

FIG. 15 is a diagram illustrating a first example of task information ofa new task created by extracting a part of a past task;

FIG. 16 is a diagram illustrating a second example of task informationof a new task created by extracting a part of the past task;

FIG. 17 is a flowchart illustrating processing when a part of the pasttask is extracted and the new task is started; and

FIG. 18 is a diagram illustrating an example of the hardwareconfiguration of a management device as an electronic blackboard.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Hereinafter, a management system 10 according to an embodiment will bedescribed in detail with reference to the drawings. The managementsystem 10 in the embodiment aims at easy access to a plurality of piecesof electronic data for which permission is given to different users.

FIG. 1 is a diagram illustrating the configuration of the managementsystem 10 in the embodiment. The management system 10 includes amanagement device 20, at least one electronic data storage device 40,and at least one terminal device 50.

The management device 20 is an information processing device having auser authentication function, an information input function, aninformation output function, a communication function, and the like. Inthe embodiment, the management device 20 is an electronic blackboard(interactive whiteboard). The management device 20 is not limited to theelectronic blackboard and may be a common computer, a tablet terminal,or a smart phone as long as a plurality of users can use the managementdevice 20. The management device 20 may be a video conference terminal,a telephone terminal such as an Internet protocol (IP) telephone and anInternet telephone, a car navigation terminal, a wearable terminal, acamera, a game console, or an industry device having a communicationfunction. The industrial device includes an office device such as amultifunction peripheral/printer/product (MFP), a medical device such asan endoscope, and an agricultural device such as a cultivator.

The management device 20 manages a task that is executed by a pluralityof users cooperatively. For example, the task is a conference that isexecuted by the users. When the task is the conference, the managementdevice 20 displays and records characters, figures, and the like writtenor drawn by the individual users, records remarks of the users, and soon in the conference. The task is not limited to the conference and maybe a creative activity, editorial work, a presentation, a seminar, andother activities that are executed by the users.

Each electronic data storage device 40 stores therein electronic dataused in the task that is managed by the management device 20. Theelectronic data storage device 40 may be any device as long as themanagement device 20 can be connected to the device. For example, theelectronic data storage device 40 may be a server device connected tothe management device 20 through a network or may be a memory card or ahard disk that is mounted on the management device 20.

The electronic data that is stored in the electronic data storage device40 can be a document, a video image, an image, and audio data. FIG. 1illustrates an example where the document is stored as an example of theelectronic data. In one example, the document may be a hypertext markuplanguage (HTML) document such as a Web page or an extensible markuplanguage (XML) document. The document may be a text data file, an imagedata file, or a presentation data file. Furthermore, the document may bea record of a database.

Each electronic data is created by the individual user in advance beforethe task that would be executed by the users cooperatively is carriedout. Permission to access (for example, refer to or update) eachelectronic data is given to a specified user (for example, user who hascreated the electronic data) and users other than the specified usercannot access the electronic data. When the electronic data is accessedfrom any information processing device, the electronic dataauthenticates whether the information processing device is a device thatis operated by the user having permission.

Authentication may be executed by any method. For example, theelectronic data may request input of a user name and a password from theinformation processing device that has accessed the electronic data andmay determine whether the input user name and password are valid.Alternatively, the electronic data may cause a card reader connected tothe information processing device that has accessed the electronic datato read information in an IC card or the like and may determine whetherthe read information is valid. Alternatively, the electronic data mayexecute the authentication with a computer program or the likeincorporated into the electronic data itself. Still alternatively, theelectronic data may redirect the access from the information processingdevice to an external authentication server and may cause theauthentication server to execute the authentication.

When each pieces of electronic data can authenticate the access from theinformation processing device that is operated by the user havingpermission, the electronic data gives authentication ticket informationto the information processing device. The authentication ticketinformation is certificate data for certificating the authentication.For example, when a web browser accesses the electronic data, theauthentication ticket information may be a cookie. When the electronicdata redirects the access to the authentication server forauthentication, the authentication server may issue the authenticationticket information. In this case, the electronic data receives theaccess from the information processing device using the authenticationticket information, without authentication processing.

The terminal device 50 may be a common computer. The terminal device 50may be a tablet terminal or a smart phone. The terminal device 50 isoperated by a user. The terminal device 50 can access the managementdevice 20 through a network.

In the management system 10, a plurality of users log in the managementdevice 20 simultaneously and execute one task cooperatively. Themanagement device 20 accesses the pieces of electronic data that havebeen created by the different users previously and are used in the task.In this case, when the management device 20 accesses the pieces ofelectronic data in a switching manner, the authentication is requestedfor the first access to the electronic data but the authentication isnot requested for second and subsequent accesses to the pieces ofelectronic data. This enables the management device 20 to easily accessthe pieces of electronic data created by the different users previously.

Furthermore, after the task is finished, the management device 20accepts access to the electronic data used in the task from the terminaldevice 50 that is operated by a first user who has participated in thetask. In this case, the management device 20 accesses the electronicdata instead of the terminal device 50 without authentication for theaccess to the electronic data.

FIG. 2 is a diagram illustrating the functional configuration of themanagement device 20. FIG. 3 is a diagram illustrating an example oftask information of a task that is being executed. FIG. 4 is a diagramillustrating an example of pieces of task information of past tasks.

The management device 20 includes a login unit 61, a logout unit 62, aninput/output unit 63, a current task storage unit 64, a past taskstorage unit 65, a management unit 66, an electronic data access unit67, an access receiver 68, and a period management unit 69.

The login unit 61 receives logins of users participating in the task.The login unit 61 authenticates the users at the time of logins. Thelogout unit 62 receives logouts of the users.

The input/output unit 63 receives input of information from the usersparticipating in the task. The input/output unit 63 outputs informationto the users participating in the task.

The current task storage unit 64 stores therein task information of thetask that is being executed. The task information of the task that isbeing executed includes a task ID for identifying the task, users(participant users) participating in the task being executed, and accessdestinations of a plurality of documents that are used in the task beingexecuted and pieces of authentication ticket information for accessingthe corresponding documents, as illustrated in FIG. 3.

The past task storage unit 65 stores therein pieces of task informationof past tasks. The task information of the past task includes, for eachpast task, a task ID, users (participant users) that have participatedin the task, access destinations of documents used in the task andpieces of authentication ticket information for accessing thecorresponding documents, and usable periods of the pieces ofauthentication ticket information, as illustrated in FIG. 4. When thetask information includes a plurality of pieces of authentication ticketinformation, the task information of the past task may include theusable periods for the respective pieces of authentication ticketinformation or may include one usable period common to the pieces ofauthentication ticket information.

The management unit 66 manages the task information of the task beingexecuted that is stored in the current task storage unit 64 and thepieces of task information of the past tasks that are stored in the pasttask storage unit 65. The management unit 66 generates the taskinformation of the task that is being executed and causes the currenttask storage unit 64 to store the task information when the task isstarted. The management unit 66 copies contents of the task informationof the task that is being executed to generate the task information ofthe past task and causes the past task storage unit 65 to store thegenerated task information additionally when the task is finished. Inthis case, the management unit 66 incorporates the usable periods of thepieces of authentication ticket information in the added taskinformation of the past task. The usable period of the authenticationticket information may be a predetermined period or a period input bythe user participating in the task.

The electronic data access unit 67 accesses the pieces of electronicdata for which permission is given to the different users. To be morespecific, when accessing a certain piece of electronic data inaccordance with an instruction from the user participating in the taskthat is being executed, the electronic data access unit 67 reads out theauthentication ticket information corresponding to the target electronicdata from the task information stored in the current task storage unit64. Then, the electronic data access unit 67 accesses the electronicdata using the read authentication ticket information.

When the task information stored in the current task storage unit 64does not include the authentication ticket information corresponding tothe target electronic data, the electronic data access unit 67 promptsthe user having the permission to input the authentication informationand accesses the electronic data. Furthermore, the electronic dataaccess unit 67 acquires the authentication ticket informationcorresponding to the accessed electronic data and writes the acquiredauthentication ticket information into the task information. With thisprocessing, the electronic data access unit 67 can access the sameelectronic data using the authentication ticket information with no needto prompt the user to input the authentication information from then on.

The access receiver 68 accepts access from the terminal device 50 thatis operated by the first user to the electronic data used in the pasttask in which the first user has participated. When receiving the accessfrom the terminal device 50 that is operated by the first user to theelectronic data, the access receiver 68 acquires the authenticationticket information included in the task information stored in the pasttask storage unit 65 and corresponding to the past task in which thefirst user has participated. Then, the access receiver 68 accesses theelectronic data instead of the terminal device 50 using the acquiredauthentication ticket information. In this case, when referring to theelectronic data, the access receiver 68 provides referred electronicdata to the terminal device 50.

When accessing the electronic data in accordance with the access fromthe terminal device 50 that is operated by the first user, the accessreceiver 68 may notify the user having the permission to access theelectronic data of the access from the first user. In one example, theaccess receiver 68 notifies the user of the access by an e-mail or othermeans. With this notification, the access receiver 68 can perform moresecure operation.

The period management unit 69 deletes the authentication ticketinformation that has reached the usable period among the pieces ofauthentication ticket information included in task information of thepast tasks stored in the past task storage unit 65. This processingenables the period management unit 69 to forbid the electronic data frombeing accessed using the authentication ticket information that hasreached the usable period.

FIG. 5 is a flowchart illustrating processing when a task is started.When starting the task, the management device 20 proceeds the processingin accordance with the flow as illustrated in FIG. 5.

First, at step S11, the management device 20 receives logins of aplurality of users. When the login operations of the users arecompleted, subsequently, the management device 20 receives a task startoperation at step S12.

Then, at step S13, the management device 20 generates new taskinformation and causes the current task storage unit 64 to store the newtask information. Subsequently, at step S14, the management device 20registers the logging-in users as the participant users in the new taskinformation. At step S15, the management device 20 starts management ofthe cooperative task that is executed by the users.

FIG. 6 is a flowchart illustrating processing when electronic data isaccessed. Although the flowchart as illustrated in FIG. 6 explains anexample when the electronic data is document, the management device 20executes similar processing on the electronic data other than document.When the document is used in the task that is being executed, themanagement device 20 proceeds the processing in accordance with the flowas illustrated in FIG. 6.

First, at step S21, the management device 20 receives an accessoperation to the document from any of the users participating in thetask. For example, when the user desires to refer to the document, themanagement device 20 receives input of information indicating an accessdestination (for example, a file name and a storage destination of afile) of the document. Alternatively, the user clicks a specific icon,whereby the management device 20 may receive the input of the accessdestination of the document corresponding to the specific icon.Furthermore, for example, when the user desires to update the document,the management device 20 receives input of the access destination of thedocument and actual data of the document to be updated.

Subsequently, at step S22, the management device 20 refers to the taskinformation of the task being executed that is stored in the currenttask storage unit 64, so as to determine whether the authenticationticket information corresponding to the input access destination of thedocument is present.

When the authentication ticket information corresponding to the inputaccess destination of the document is present in the task information ofthe task being executed (Yes at step S22), the management device 20proceeds the processing to step S23. At step S23, the management device20 acquires the corresponding authentication ticket information from thetask information. Subsequently, at step S24, the management device 20accesses the document indicated by the input access destination usingthe acquired authentication ticket information. When receiving theaccess using the valid authentication ticket information, the documentaccepts the access without requesting for the authentication. Forexample, when the document is accessed for reference, the managementdevice 20 acquires the document from the electronic data storage device40 and provides the document thus acquired to the user. The managementdevice 20 finishes this flow with completion of the processing at stepS24.

When the authentication ticket information corresponding to the inputaccess destination of the document is not present in the taskinformation of the task being executed (No at step S22), the managementdevice 20 proceeds the processing to step S25. At step S25, themanagement device 20 receives an authentication request from thedocument indicated by the input access destination and prompts the userhaving the permission to input the authentication information. When theinput authentication information is valid, the document accepts theaccess.

When the authentication information is valid, subsequently, themanagement device 20 accesses the document at step S26. For example,when the document is accessed for reference, the management device 20acquires the document from the electronic data storage device 40 andprovides the document thus acquired to the user. Thereafter, at stepS27, the management device 20 acquires the authentication ticketinformation from the accessed document. At step S28, the managementdevice 20 registers the acquired authentication ticket information andthe access destination of the document in the task information of thetask that is being executed. This registration enables the managementdevice 20 to access the same document using the authentication ticketinformation with no need to prompt the user to input the authenticationinformation when the management device 20 accesses the document fromthen on. The management device 20 finishes this flow with completion ofthe processing at step S28.

FIG. 7 is a flowchart illustrating processing when a task is finished.Although the flowchart as illustrated in FIG. 7 explains an example whenthe electronic data is document, the management device 20 executessimilar processing on the electronic data other than document. Themanagement device 20 proceeds the processing in accordance with the flowas illustrated in FIG. 7 when finishing the task.

First, at step S41, the management device 20 receives a task finishoperation. Subsequently, at step S42, the management device 20 sets theusable periods of the documents used in the task. The management device20 may set predetermined periods as the usable periods or may prompt theusers participating in the task to input the usable periods.

Subsequently, at step S43, the management device 20 additionally stores,as the task information of the past task, contents included in the taskinformation of the task being executed and the set usable periods in thepast task storage unit 65. After the additional storing, the managementdevice 20 deletes the task information of the task being executed fromthe current task storage unit 64. Then, at step S44, the managementdevice 20 finishes the task that is being executed.

FIG. 8 is a sequence diagram illustrating processing when the terminaldevice 50 accesses the document after the task is finished. The usersthat have participated in the task can access the documents used in thetask through the management device 20 before the usable periods of thedocuments expire even when the users do not have the permissiontherefor. In this case, the management device 20 proceeds the processingin accordance with the sequence as illustrated in FIG. 8.

The terminal device 50 logs in the management device 20 through anetwork in accordance with an operation by the first user (S50). Whenthe login operation is succeeded, subsequently, the terminal device 50specifies a task ID and information indicating an access destination(for example, a file name and a storage destination of a file) of adocument and transmits, to the management device 20, an access requestto the document (S51).

Upon receiving the access request, the access receiver 68 of themanagement device 20 refers to the task information of the past taskcorresponding to the specified task ID in the past task storage unit 65(S52 and S53). Then, the access receiver 68 checks whether theparticipant users in the task information corresponding to the specifiedtask ID include the first user (S54). When the first user is notincluded therein as a result of the check, the access receiver 68notifies the terminal device 50 of access failure and finishes theprocessing.

When the participant users include the first user, the access receiver68 acquires the authentication ticket information of the specifieddocument from the task information of the past task corresponding to thespecified task ID (S55 and S56). When the authentication ticketinformation is not present because of expiration of the usable period,for example, the access receiver 68 notifies the terminal device 50 ofaccess failure and finishes the processing.

When the access receiver 68 acquires the authentication ticketinformation, it accesses the specified access destination of thedocument using the authentication ticket information (S57 and S58). Whenthe document is accessed for reference, the access receiver 68transmits, to the terminal device 50, the document acquired by referring(S59). Then, the access receiver 68 notifies the user having thepermission for the accessed document of the access from the first userby an E-mail or other means (S60).

As described above, according to the management device 20 in theembodiment, when the first access to the document by is authenticated,the management device 20 can access the same document withoutauthentication from then on even after the document to be accessed isswitched. Accordingly, the management device 20 can easily access aplurality of documents for which different users have permission whenthe users carry out the task cooperatively.

Furthermore, the management device 20 receives access from the firstuser who has participated in the task using the terminal device 50 tothe document used in the task after the task is finished. In this case,the management device 20 accesses the document instead of the terminaldevice 50. Accordingly, the management device 20 enables easy access tothe documents that have been used in the task executed by the userscooperatively and for which permission is given to the different users.

It should be noted that, for example, the document may be a web page forbooking a conference room, a web page for booking facility, and a webpage for control to operate a device. In this case, after the task isfinished, other users can access the web page that only a certain userhaving permission could have accessed during the task, instead of thecertain user. Accordingly, the management device 20 in the embodimentcan therefore control access more flexibly.

FIG. 9 is a diagram illustrating examples of login timings and logouttimings of users and the users that have participated in tasks. Timingsat which the tasks are started and finished may not be timings at whichthe users instruct to start and finish the tasks clearly but may betimings at which any user logs in or logs out. In this case, themanagement unit 66 manages one task, as a unit, from the time at whichthe users access simultaneously and any user logs in or logs out to thetime at which any user logs in or logs out next.

In the management, the management unit 66 incorporates the login timeand the logout time of each user in the task information of the pasttask. The management unit 66 specifies the participant users in eachtask based on the login time and the logout time of the users.

For example, as illustrated in FIG. 9, it is assumed that a user A logsin at the time t0, a user B logs in at the time t1 after the time t0,and a user C logs in at the time t2 after the time t1. It is assumedthat the user A logs out at the time t3 after the time t2 and the user Blogs out at the time t4 after the time t3. Furthermore, it is assumedthat a user D logs in at the time t5 after the time t4, the user C logsout at the time t6 after the time t5, and the user D logs out at thetime t7 after the time t6.

In this case, the participant users of a task a between the time t1 andthe time t2 are the user A and the user B. The participant users of atask b between the time t2 and the time t3 are the user A, the user B,and the user C. The participant users of a task c between the time t3and the time t4 are the user B and the user C. The participant users ofa task d between the time t5 and the time t6 are the user C and the userD. As described above, the management unit 66 incorporates the logintime and the logout time of each user in the task information, therebyspecifying the users participating in each task.

FIG. 10 is a diagram illustrating examples of the login timings and thelogout timings of the users and documents that are used in each task.Although FIG. 10 explains an example when the electronic data isdocument, the management device 20 executes similar processing on theelectronic data other than document. When the management unit 66 managesone task, as a unit, from the time at which the users accesssimultaneously and any user logs in or logs out to the time at which anyuser logs in or logs out next, the management unit 66 incorporatesaccess timings to the documents in the task information of each pasttask. The management unit 66 specifies the documents used in each taskbased on the access timings to the documents.

For example, as illustrated in FIG. 10, a document α is accessed betweenthe time t1 and the time t2 and between the time t2 and the time t3. Adocument β is accessed between the time t2 and the time t3 and betweenthe time t3 and the time t4. A document γ is accessed between the timet3 and the time t4 and between the time t5 and the time t6. A document δis accessed between the time t5 and the time t6.

In this case, the document used in the task a between the time t1 andthe time t2 is the document α. The documents used in the task b betweenthe time t2 and the time t3 are the document α and the document β. Thedocuments used in the task c between the time t3 and the time t4 are thedocument β and the document γ. The documents used in the task d betweenthe time t5 and the time t6 are the document γ and the document δ. Asdescribed above, the management unit 66 incorporates the access timingsto the documents in the pieces of task information, thereby specifyingthe documents used in each task.

FIG. 11 is a diagram illustrating task information of a new task takingover a past task. Although FIG. 11 explains an example when theelectronic data is document, the management device 20 executes similarprocessing on the electronic data other than document. For example, whenthe management unit 66 of the management device 20 starts the new task,it may generate the task information of the new task based on the taskinformation of the past task. In this case, the management unit 66 maygenerate the task information of the new task while taking over the taskinformation of the past task as it is.

For example, as illustrated in FIG. 11, the management unit 66 generatesthe task information of the new task while taking over the participantusers, and the access destinations and the pieces of authenticationticket information of the documents that are included in the taskinformation of any of the past tasks stored in the past task storageunit 65. With this, when the management unit 66 continues the past taskor carries out the task with the same theme regularly, the managementunit 66 can carry out the new task while taking over the pastinformation as it is.

FIG. 12 is a flowchart illustrating processing when the new task isstarted while taking over the past task. Although the flowchart asillustrated in FIG. 12 explains an example when the electronic data isdocument, the management device 20 executes similar processing on theelectronic data other than document. When starting the new task takingover the past task, the management unit 66 proceeds the processing inaccordance with the flow as illustrated in FIG. 12.

First, at step S111, the management unit 66 receives a start operationof the new task. Subsequently, at step S112, the management unit 66inquires at a user whether to take over the past task.

When the new task does not take over the past task (No at S112), at stepS113, the management unit 66 generates new task information and causesthe current task storage unit 64 to store the new task information.Subsequently, at step S114, the management unit 66 registers thelogging-in users as the participant users in the new task information.At step S120, the management unit 66 starts the cooperative task by theusers.

When the new task takes over the past task (Yes at S112), at step S115,the management unit 66 extracts pieces of task information of past tasksall the participating users of which are included in the logging-inusers from the past task storage unit 65 and provides the taskinformation thus extracted. To be more specific, the management unit 66extracts the pieces of task information of the past tasks theparticipant users of which are totally identical to the logging-inusers, as well as the pieces of task information of the past tasks theparticipant users of which are totally identical to some of thelogging-in users, and then provides the pieces of task information thusextracted.

Thereafter, at step S116, the management unit 66 receives selection ofthe task information of any one past task among the pieces of taskinformation of the past tasks that have been provided. Then, at stepS117, the management unit 66 generates the new task information andcauses the current task storage unit 64 to store the new taskinformation. At step S118, the management unit 66 registers thelogging-in users as the participant users in the new task information.Subsequently, at step S119, the management unit 66 registers the accessdestinations and the pieces of authentication ticket information of thedocuments that are included in the selected task information of the pasttask in the task information of the new task.

At step S120, the management unit 66 starts the cooperative task by theusers. In this manner, the management unit 66 can generate the taskinformation of the new task while taking over the task information ofthe past task all the participating users of which are included in thelogging-in users and start the new task.

FIG. 13 is a diagram illustrating task information of a new task createdby combining a plurality of past tasks. Although FIG. 13 explains anexample when the electronic data is document, the management device 20executes similar processing on the electronic data other than document.The management unit 66 may generate the task information of the new taskcreated by combining the pieces of task information of the past tasks.

For example, as illustrated in FIG. 13, the management unit 66 generatesthe task information of the new task by combining the participant users,and the access destinations and the pieces of authentication ticketinformation of the documents that are included in the pieces of taskinformation of any of the past tasks stored in the past task storageunit 65. With this, when the management unit 66 integrates two tasksinto one task, the management unit 66 can cause the new task to takeover contents of the respective tasks.

FIG. 14 is a flowchart illustrating processing when the past tasks arecombined and the new task is started. Although the flowchart asillustrated in FIG. 14 explains an example when the electronic data isdocument, the management device 20 executes similar processing on theelectronic data other than document. When starting the new task createdby combining the past tasks, the management unit 66 proceeds theprocessing in accordance with the flow as illustrated in FIG. 14.

First, at step S131, the management unit 66 receives a task combinationoperation. Subsequently, at step S132, the management unit 66 extractspieces of task information of past tasks all the participating users ofwhich are included in the logging-in users from the past task storageunit 65 and provides the pieces of task information thus extracted.Thereafter, at step S133, the management unit 66 receives selection ofthe pieces of task information of any of the past tasks among the piecesof task information of the past tasks that have been provided.

Then, at step S134, the management unit 66 generates the new taskinformation and causes the current task storage unit 64 to store the newtask information. Subsequently, at step S135, the management unit 66registers the logging-in users as the participant users in the new taskinformation. At step S136, the management unit 66 registers the accessdestinations and the pieces of authentication ticket information of thedocuments that are included in the selected pieces of task informationof the past tasks in the task information of the new task.

At step S137, the management unit 66 starts the cooperative task by theusers. In this manner, the management unit 66 can generate the taskinformation of the new task by combining the pieces of task informationof the past tasks and start the new task.

FIG. 15 is a diagram illustrating a first example of task information ofa new task created by extracting a part of a past task. FIG. 16 is adiagram illustrating a second example of task information of a new taskcreated by extracting a part of the past task. The management unit 66may generate the task information of the new task by extracting a partof the task information of the past task. Although FIG. 15 and FIG. 16explain examples when the electronic data is document, the managementdevice 20 executes similar processing on the electronic data other thandocument.

For example, as illustrated in FIG. 15, the management unit 66 generatesthe task information of the new task by extracting some users of theparticipant users that are included in the task information of any oneof the past tasks stored in the past task storage unit 65.Alternatively, for example, as illustrated in FIG. 16, the managementunit 66 generates the task information of the new task by extractingsome access destinations and pieces of authentication ticket informationof the access destinations and the pieces of authentication ticketinformation of the documents that are included in the task informationof any one of the past tasks stored in the past task storage unit 65.With this, when one task is contracted or one task is divided into aplurality of tasks, the management unit 66 can cause the new task totake over a part of the contents of the task.

FIG. 17 is a flowchart illustrating processing when a part of the pasttask is extracted and the new task is started. Although the flowchart asillustrated in FIG. 17 explains an example when the electronic data isdocument, the management device 20 executes similar processing on theelectronic data other than document. When extracting a part of the pasttask and starting the new task, the management unit 66 proceeds theprocessing in accordance with the flow as illustrated in FIG. 17.

First, at step S141, the management unit 66 receives an extractionoperation of a part of the task. Subsequently, step S142, the managementunit 66 extracts pieces of task information of past tasks all theparticipating users of which are included in the logging-in users fromthe past task storage unit 65 and provides the pieces of taskinformation thus extracted. Thereafter, at step S143, the managementunit 66 receives selection of the task information of any one past taskamong the pieces of task information of the past tasks that have beenprovided.

Then, at step S144, the management unit 66 generates the new taskinformation and causes the current task storage unit 64 to store the newtask information. Subsequently, at step S145, the management unit 66registers some or all of the participant users included in the selectedtask information of the past task as the participant users in the newtask information. The management unit 66 can extract some of theparticipant users in the past task by registering some of theparticipant users.

At step S146, the management unit 66 registers the access destinationsand the pieces of authentication ticket information of some or all ofthe documents for which the users registered at step S145 havepermission among the access destinations and the pieces ofauthentication ticket information of the documents that are included inthe selected task information of the past task. The management unit 66can extract the access destinations and the pieces of authenticationticket information of the documents in the past task by registering someof the access destinations and the pieces of authentication ticketinformation of the documents.

At step S147, the management unit 66 starts the cooperative task by theusers. In this manner, the management unit 66 can generate the taskinformation of the new task by extracting a part of the task informationof the past task and start the new task.

FIG. 18 is a diagram illustrating an example of the hardwareconfiguration of the management device 20 as an electronic blackboard.The management device 20 as the electronic blackboard includes a centralprocessing unit (CPU) 221, a read only memory (ROM) 222, a random accessmemory (RAM) 223, a flash memory 224, a solid state drive (SSD) 225, ahard disk (HD) 226, a hard disk drive (HDD) 227, a network interface(I/F) 228, a medium drive 229, an audio input/output I/F 231, an imageinput I/F 232, a capture device 233, a graphics processing unit (GPU)234, a display 220, a display controller 235, a touch sensor 236, asensor controller 237, an electronic pen controller 238, and a bus line240.

The CPU 221 controls the entire operations of the management device 20as the electronic blackboard. The ROM 222 stores therein a computerprogram that is used for driving the CPU 221. The RAM 223 is used as awork area of the CPU 221. The flash memory 224 stores therein variousdata such as the control computer program for the management device 20as the electronic blackboard. The management device 20 as the electronicblackboard may include an electrically erasable programmable read-onlymemory (EEPROM) or the like instead of the flash memory 224. The SSD 225controls reading or writing of the various data from or into the flashmemory 224 in accordance with control by the CPU 221.

The HD 226 stores therein pieces of data, the computer program, andother items. The HDD 227 controls reading or writing of the various datafrom or into the HD 226 in accordance with control by the CPU 221.

The network I/F 228 controls communications performed through a network.The medium drive 229 controls reading or writing (storage) of pieces ofdata from or into a recording medium such as a flash memory that can bedetachably attached to the management device 20 as the electronicblackboard. The audio input/output I/F 231 processes input/output of anaudio signal to and from a microphone speaker or the like in accordancewith control by the CPU 221.

The image input I/F 232 inputs an image shot by a camera. For example,the capture device 233 captures a still image or a video image displayedon a display of another computer. The GPU 234 executes graphicsprocessing. The GPU 234 executes image drawing processing based oninformation input by a user. The GPU 234 executes processing ofsynthesizing a drawn image, an image taken by the capture device 233,and an image input from the camera. The display controller 235 controlsand manages screen display for outputting the output image from the GPU234 to the display 220.

The touch sensor 236 detects a touch operation and input of informationonto the display 220 by an electronic pen or a user's hand. The sensorcontroller 237 controls processing of the touch sensor 236 in accordancewith control by the CPU 221.

The touch sensor 236 inputs coordinates and detects coordinates by aninfrared ray cut method, as an example. A method of inputting thecoordinates and detecting the coordinates is the following method. Thatis, a method in which two light emitting/receiving devices installed onboth upper end portions of the display 220 emit a plurality of infraredrays in parallel with the display 220 and light receiving elementsreceive light reflected by a reflecting member provided on the peripheryof the display 220 and returned along light paths same as the lightpaths of the emitted light is employed. The touch sensor 236 outputs, tothe sensor controller 237, the identifications (IDs) of the infraredrays emitted from the two light emitting/receiving devices that areblocked by a substance. The sensor controller 237 specifies a coordinateposition as a touched position of the substance.

Furthermore, as the touch sensor 236, various detection units such as anelectrostatic capacitance-type touch panel specifying the touchedposition by detecting change in electrostatic capacitance, a resistancefilm-type touch panel specifying the touched position by detectingchange in voltages of opposing two resistance films, an electromagneticinduction-type touch panel specifying the touched position by detectingelectromagnetic induction generated by touching the contact substancewith the display unit can be employed without being limited to theinfrared ray cut method.

The electronic pen controller 238 communicates with the electronic penso as to determine whether the tip or the tail of the electronic pentouches the display 220. It should be noted that the electronic pencontroller 238 may determine whether a portion of the electronic penthat is gripped by a user or another portion of the electronic pen, inaddition to the tip or the tail of the electronic pen, touches thedisplay 220.

The bus line 240 is a component, such as an address bus and a data bus,for connecting the constituent components.

The computer program that is executed by the management device 20 as theelectronic blackboard has a module configuration including a loginmodule, a logout module, an input/output module, a current task storagemodule, a past task storage module, a management module, an electronicdata access module, a remote access module, and a period managementmodule. The CPU 221 (processor) loads and executes the computer programon the RAM 223 so as to cause the management device 20 as the electronicblackboard to function as the login unit 61, the logout unit 62, theinput/output unit 63, the current task storage unit 64, the past taskstorage unit 65, the management unit 66, the electronic data access unit67, the access receiver 68, and the period management unit 69.

It should be noted that the management device 20 is not limited to havethe configuration as described above and may have a configuration inwhich at least a part of the login unit 61, the logout unit 62, theinput/output unit 63, the current task storage unit 64, the past taskstorage unit 65, the management unit 66, the electronic data access unit67, the access receiver 68, and the period management unit 69 is made tooperate by a hardware circuit (for example, a semiconductor integratedcircuit).

The computer program that is executed by the management device 20 in theembodiment is recorded and provided in a computer-readable recordingmedium, such as a compact disc read only memory (CD-ROM), a flexibledisk (FD), a compact disc recordable (CD-R), and a digital versatiledisc (DVD), as an installable or executable file.

The computer program that is executed by the management device 20 in theembodiment may be stored in a computer connected to a network such asthe Internet and provided by being downloaded via the network.Furthermore, the computer program that is executed by the managementdevice 20 in the embodiment may be provided or distributed via a networksuch as the Internet. For example, the computer program that is executedby the management device 20 may be incorporated and provided in a ROM.

The present invention provides an effect that a new task can be easilyset when a plurality of users carry out the task cooperatively.

Although the invention has been described with respect to specificembodiments for a complete and clear disclosure, the appended claims arenot to be thus limited but are to be construed as embodying allmodifications and alternative constructions that may occur to oneskilled in the art that fairly fall within the basic teaching herein setforth.

The present invention can be implemented in any convenient form, forexample using dedicated hardware, or a mixture of dedicated hardware andsoftware. The present invention may be implemented as computer softwareimplemented by one or more network processing apparatus. The network cancomprise any conventional terrestrial or wireless communicationsnetwork, such as the Internet. The processing apparatus can compromiseany suitably programmed apparatuses such as a general purpose computer,personal digital assistant, mobile telephone (such as a WAP or3G-compliant phone) and so on. Since the present invention can beimplemented as software, each and every aspect of the present inventionthus encompasses computer software implemental on a programmable device.The computer software can be provided to the programmable device usingany storage medium for storing processor readable code such as a floppydisk, hard disk, CD ROM, magnetic tape device or solid state memorydevice.

The hardware platform includes any desired kind of hardware resourcesincluding, for example, a central processing unit (CPU), a random accessmemory (RAM), and a hard disk drive (HDD). The CPU may be implemented byany desired kind of any desired number of processor. The RAM may beimplemented by any desired kind of volatile or non-volatile memory. TheHDD may be implemented by any desired kind of non-volatile memorycapable of storing a large amount of data. The hardware resources mayadditionally include an input device, an output device, or a networkdevice, depending on the type of the apparatus. Alternatively, the HDDmay be provided outside of the apparatus as long as the HDD isaccessible. In this example, the CPU, such as a cache memory of the CPU,and the RAM may function as a physical memory or a primary memory of theapparatus, while the HDD may function as a secondary memory of theapparatus.

What is claimed is:
 1. A management device that manages a task that isexecuted by a plurality of users cooperatively, the management devicecomprising: a memory storing a program of instructions; and a processorconfigured to execute the program of instructions to manage acooperative computing task executed by the plurality of users, themanaging including generating an instance of task information associatedwith the cooperative computing task, associating the instance of taskinformation with the plurality of users and one or more instances ofelectronic data associated with the cooperative computing task, the oneor more instances of electronic data stored at one or more electronicdata storage devices that are separate from the management device, suchthat the instance of task information includes participant userinformation indicating a plurality of participant users associated withthe cooperative computing task, access destination informationindicating a destination of the one or more instances of electronic dataassociated with the cooperative computing task, and authenticationticket information indicating authentication of the one or moreinstances of electronic data associated with the cooperative computingtask, and selectively enabling access by at least one user of theplurality of users to a particular instance of electronic dataassociated with a particular cooperative computing task through themanagement device based on determining that the at least one user and aninstance of authentication ticket information of the particular instanceof electronic data are both associated with a particular instance oftask information associated with the particular cooperative computingtask, and generate a new instance of task information associated with anew cooperative computing task based on a past instance of taskinformation associated with a past cooperative computing task previouslyexecuted using the management device.
 2. The management device accordingto claim 1, wherein generating the new instance of task informationincludes causing the new instance of task information to include commonparticipant user information with common participant user information ofthe past instance of task information, an entirety of users indicated inthe participant user information associated with the past instance oftask information being included in the plurality of users.
 3. Themanagement device according to claim 1, wherein generating the newinstance of task information includes combining a plurality of instancesof information associated with separate, respective past instances oftask information to be a plurality of instances of informationassociated with the new instance of task information, an entirety ofusers indicated in the participant user information associated with atleast one past instance of task information of the plurality of pastinstances of task information being included in the plurality of users.4. The management device according to claim 1, wherein generating thenew instance of task information includes extracting at least a limitedportion of information associated with the past instance of taskinformation to be an instance of information associated with the newinstance of task information, an entirety of users indicated in theparticipant user information associated with the past instance of taskinformation being included in the plurality of users.
 5. The managementdevice according to claim 4, wherein generating the new instance of taskinformation includes registering at least a limited portion of users ofthe users indicated in the participant user information associated withthe past instance of task information being included in the plurality ofusers as one or more participant users indicated in participant userinformation of the new instance of task information.
 6. The managementdevice according to claim 4, wherein the generating the new instance oftask information includes registering at least a limited portion ofaccess destination information of the past instance of task informationas access destination of the new instance of task information.
 7. Amanagement method of managing a task that is executed by a plurality ofusers cooperatively by a management device, the method comprising:managing a cooperative computing task executed by the plurality ofusers, the managing including generating an instance of task informationassociated with the cooperative computing task, associating the instanceof task information with the plurality of users and one or moreinstances of electronic data associated with the cooperative computingtask, the one or more instances of electronic data stored at one or moreelectronic data storage devices that are separate from the managementdevice, such that the instance of task information includes participantuser information indicating a plurality of participant users associatedwith the cooperative computing task, access destination informationindicating a destination of the one or more instances of electronic dataassociated with the cooperative computing task, and authenticationticket information indicating authentication of the one or moreinstances of electronic data associated with the cooperative computingtask, and selectively enabling access by at least one user of theplurality of users to a particular instance of electronic dataassociated with a particular cooperative computing task through themanagement device based on determining that the at least one user and aninstance of authentication ticket information of the particular instanceof electronic data are both associated with a particular instance oftask information associated with the particular cooperative computingtask; and generating a new instance of task information associated witha new cooperative computing task based on a past instance of taskinformation associated with a past cooperative computing task previouslyexecuted using the management device.
 8. The method according to claim7, wherein generating the new instance of task information includescausing the new instance of task information to include commonparticipant user information with common participant user information ofthe past instance of task information, an entirety of users indicated inthe participant user information associated with the past instance oftask information being included in the plurality of users.
 9. The methodaccording to claim 7, wherein generating the new instance of taskinformation includes combining a plurality of instances of informationassociated with separate, respective past instances of task informationto be a plurality of instances of information associated with the newinstance of task information, an entirety of users indicated in theparticipant user information associated with at least one past instanceof task information of the plurality of past instances of taskinformation being included in the plurality of users.
 10. The methodaccording to claim 7, wherein generating the new instance of taskinformation includes extracting at least a limited portion ofinformation associated with the past instance of task information to bean instance of information associated with the new instance of taskinformation, an entirety of users indicated in the participant userinformation associated with the past instance of task information beingincluded in the plurality of users.
 11. The method according to claim10, wherein generating the new instance of task information includesregistering at least a limited portion of users of the users indicatedin the participant user information associated with the past instance oftask information being included in the plurality of users as one or moreparticipant users indicated in participant user information of the newinstance of task information.
 12. The method according to claim 10,wherein the generating the new instance of task information includesregistering at least a limited portion of access destination informationof the past instance of task information as access destination of thenew instance of task information.
 13. A non-transitory computer-readablemedium storing a program of instructions that, when executed by aninformation processing device, cause the information processing deviceto perform a method of managing a task that is executed by a pluralityof users cooperatively by a management device, the method comprising:managing a cooperative computing task executed by the plurality ofusers, the managing including generating an instance of task informationassociated with the cooperative computing task, associating the instanceof task information with the plurality of users and one or moreinstances of electronic data associated with the cooperative computingtask, the one or more instances of electronic data stored at one or moreelectronic data storage devices that are separate from the managementdevice, such that the instance of task information includes participantuser information indicating a plurality of participant users associatedwith the cooperative computing task, access destination informationindicating a destination of the one or more instances of electronic dataassociated with the cooperative computing task, and authenticationticket information indicating authentication of the one or moreinstances of electronic data associated with the cooperative computingtask, and selectively enabling access by at least one user of theplurality of users to a particular instance of electronic dataassociated with a particular cooperative computing task through themanagement device based on determining that the at least one user and aninstance of authentication ticket information of the particular instanceof electronic data are both associated with a particular instance oftask information associated with the particular cooperative computingtask; and generating a new instance of task information associated witha new cooperative computing task based on a past instance of taskinformation associated with a past cooperative computing task previouslyexecuted using the management device.
 14. The non-transitorycomputer-readable medium according to claim 13, wherein generating thenew instance of task information includes causing the new instance oftask information to include common participant user information withcommon participant user information of the past instance of taskinformation, an entirety of users indicated in the participant userinformation associated with the past instance of task information beingincluded in the plurality of users.
 15. The non-transitorycomputer-readable medium according to claim 13, wherein generating thenew instance of task information includes combining a plurality ofinstances of information associated with separate, respective pastinstances of task information to be a plurality of instances ofinformation associated with the new instance of task information, anentirety of users indicated in the participant user informationassociated with at least one past instance of task information of theplurality of past instances of task information being included in theplurality of users.
 16. The non-transitory computer-readable mediumaccording to claim 13, wherein generating the new instance of taskinformation includes extracting at least a limited portion ofinformation associated with the past instance of task information to bean instance of information associated with the new instance of taskinformation, an entirety of users indicated in the participant userinformation associated with the past instance of task information beingincluded in the plurality of users.
 17. The non-transitorycomputer-readable medium according to claim 16, wherein generating thenew instance of task information includes registering at least a limitedportion of users of the users indicated in the participant userinformation associated with the past instance of task information beingincluded in the plurality of users as one or more participant usersindicated in participant user information of the new instance of taskinformation.
 18. The non-transitory computer-readable medium accordingto claim 16, wherein the generating the new instance of task informationincludes registering at least a limited portion of access destinationinformation of the past instance of task information as accessdestination of the new instance of task information.